Repository navigation
perf(render): scale screen geometry budgets to plot size - #179
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reduce excess screen geometry for small plots by scaling line sampling and overview contour budgets to their displayed size. Line pooling retains extrema, enlarged contours return to full geometry, and figure exports keep their existing rendering paths. Document the screen-detail behavior in English and Chinese.
Add a synthetic workspace benchmark that waits for settled Full detail and reports UI construction plus tessellation CPU time and vertex counts for 12, 60, 120, and 500 canvases.
Validation
cargo pr-check— passed on Windows.npm run buildindocs/— passed.cargo test --release -p plotium bench_stress_workspace -- --ignored --nocapture— passed. On Windows at 1600×1000, overview CPU medians for 12/60/120/500 canvases were 6.14/17.25/40.66/119.54 ms; single-canvas medians were 3.97/4.81/5.85/8.56 ms. These measure UI construction and tessellation only, not GPU or end-to-end frame time.